Skip to content

Comments

[18.0][MIG] uom_category_active: Migration to version 18.0#2221

Open
takahii03 wants to merge 8 commits intoOCA:18.0from
takahii03:18.0-uom_category_active-mig
Open

[18.0][MIG] uom_category_active: Migration to version 18.0#2221
takahii03 wants to merge 8 commits intoOCA:18.0from
takahii03:18.0-uom_category_active-mig

Conversation

@takahii03
Copy link
Member

Hi, all.
The changes are mostly standard migration steps, with the exception of renaming a test class name to better align with current naming conventions.

Everything else followed the usual migration process.
Could you could take a look @angelmoya ?

@yostashiro
Copy link
Member

@takahii03 Thanks for the migration! Commit history must be preserved. Can you please follow the steps described in https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-18.0#technical-method-to-migrate-a-module-from-170-to-180-branch?

@takahii03 takahii03 force-pushed the 18.0-uom_category_active-mig branch from 4e2c612 to 023b9db Compare February 24, 2026 12:05
@takahii03
Copy link
Member Author

@yostashiro
Thank you for pointing that out!
I have included the commits related to the changes in uom_category_active from version 17.0 to 18.0.
I’ve also filtered out bot-generated commits to keep the history clean.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants